Changes between Version 5 and Version 6 of Development FAQ

Timestamp:

Apr 27, 2007, 8:39:48 PM (17 years ago)

Author:

John Bailey

Comment:

--

Development FAQ

@@ -41 +41 @@
 Without this, on Windows systems the opened files will use Windows default translation (<CR><LF> for newline, for example).  This will cause errors due to newline format and the "bytes read" counts, which will be wrong when comparing the return value of `read()` to `stat()`.
 
-=== Why are there `G_DIR_SEPARATOR_S` and `G_DIR_SEPARATOR` usages everywhere? ===
+=== Why is `G_DIR_SEPARATOR_S` and `G_DIR_SEPARATOR` used everywhere? ===
 This is a matter of maintaining cross-platform compatibility.  Windows uses a backslash ("\") for directory separators in paths, while UNIX-like systems use the forward slash ("/").  Other OSes may choose to use other separators--for example, prior to Mac OS X, it was common for the directory separator on Macs to be a colon (":").  It is impractical to use preprocessor directives throughout the code to determine the path style to use, especially if a new OS were to appear and use a different directory separator.  GLib, which we already use, provides the convenient separator macro, so we use this to reduce our code complexity and maintain cross-platform portability.
 
@@ -50 +50 @@
 === Should I use `snprintf()` or `vsnprintf()`? ===
 No.  Use the GLib wrapper functions instead.  They are `g_snprintf()` and `g_vsnprintf`.
+
+=== How do I get the settings directory? ===
+Use `purple_home_dir()`.  You should ''not'' use `g_get_home_dir()` or `getenv("HOME")`.
 
 == Headers ==